[8.0] JobAgent - do not fail already rescheduled job #8427
+27
−18
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
atsareg
added
the
alsoTargeting:integration
atsareg
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Jobs that failed initialization, e.g. input sandbox download, are rescheduled by the jobwrapper and return non-zero status. JobAgent checks the job status with a certain delay, can be few minutes in the case of Pool/Singularity inner CE. The job can be already rescheduled, matched and running on another site again by this time. JobAgent sets the job status to Failed if it is in a Running status even if it is running after a successful rescheduling elsewhere. This Failed status is false in this case and should not be set.
BEGINRELEASENOTES
*WorkloadManagement
FIX: JobAgent - do not fail already rescheduled job
ENDRELEASENOTES